Activity computer systems

ABSTRACT

In one implementation, a system for broadcasting on-duty adventure opportunities among computing devices includes an adventure management computer system to transmit (a) push notifications to selected mobile computing devices related to activated on-duty adventure opportunities and (b) local beacon signal identifiers for mobile-to-mobile beacon signal transmissions for the activated on-duty adventure opportunities, a guide mobile computing device to locally broadcast information for the on-duty adventure opportunity, and a participant mobile computing device (i) to detect the local beacon signals with the local beacon signal identifier for the on-duty adventure opportunity, (ii) to obtain the adventure information for the on-duty adventure opportunity from the adventure management computer system, and (iii) to reserve the on-duty adventure opportunity with the adventure management computer system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/484,222, filed on Aug. 7, 2019, which is a National Stage Applicationunder 35 U.S.C. § 371 of International Application No.PCT/US2018/017217, filed on Feb. 7, 2018, which claims priority to U.S.Application Ser. No. 62/455,886, filed on Feb. 7, 2017. The disclosuresof the prior application are incorporated by reference in theirentirety.

TECHNICAL FIELD

This document generally describes technological improvements to userinterfaces and computer systems for connecting users with sources ofoutdoor guide opportunities or other activities.

BACKGROUND

Outdoor guides can be experts in one or more outdoor activities, likehunting or fishing, and provide guiding services for clients related totheir areas of expertise. In general, guide services can include avariety of different activities, such as instructing beginners orenthusiasts on one or more outdoor skills (e.g., casting techniques forfly fishing), introducing users to particular outdoor locations (e.g.,bringing users to a particularly good hunting location), and/or guidingusers on an outdoor experience (e.g., taking users on a hunting trip).Typically, an expert guide is hired by users on a per trip or perexperience basis, which can last anywhere from a couple hours to acouple weeks (or longer).

Users have located guides in a number of ways, such as through word ofmouth referrals, recommendations through hospitality services (e.g.,concierge services), online advertising, and internet searches. Forexample, an outdoor guide may have an individual website to describehis/her services and may also purchase online advertising on socialnetworking and internet search platforms. Prospective and existing userscan locate and connect with this outdoor guide in a variety of ways,such as through entering the uniform resource locator (URL) for theguide's website into a web browser, conducting an internet search forthe guide (which can link back to the guide's website), and/or selectingan online advertisement for the guide (which can also link back to theguide's website).

SUMMARY

This document generally describes technology for an improved platformand mobile user interface that optionally combines social media aspectswith activity sourcing capabilities for connecting users with sources ofoutdoor guide opportunities or other activities. Such connectionsbetween users and guide opportunities can be made based on any of avariety of factors, such as location, time of day, date, available orrequired equipment, range of costs, cost-sharing bid opportunities,stored user preferences, historical reviews from previous users, auser-specific input level of adventure/risk, or the like. In particularembodiments, the improved platform and user interface features can beimplemented in a manner that allows for users and/or adventure providers(e.g., guides) to be rapidly on-boarded (enrolled) to the platform.

In one example, such an improved platform can be more technicallycomplex than a conventional social media platform based on adventureopportunities and all of the corresponding facets of scheduling,booking, and fulfilling adventures. Accordingly, on-boarding users tothis example of the platform can reduce or eliminate multiple anditerative different requests to the user for information, which can betime consuming and difficult to fulfill depending on the user's devicetype (e.g., smartwatch, smartphone, wearable computing device, tablet).The improved platform can streamline the onboarding process through aset of non-conventional user interface features that prompt the user forminimal information on the front end by accessing user information fromother sources and/or delaying obtaining such information from the useruntil one or more later points in time. By offloading the burden onusers through non-conventional user interface features, the improvedplatform can provide an on-boarding process that can remove barriers toentry and participation for users.

Once on-boarded, the improved platform can provide a guide-pairingcomputer system configured to pair users seeking a physical activity(e.g., either a specific, predetermined activity or a spontaneous,previously unplanned or unknown activity) with a variety of filteredsources for such activity. Such computer systems can use internet-basedtechnology to assist users in identifying, connecting with, andreserving an activity from a set of selectable adventures (e.g., outdoorguide trips, outdoor guided experiences, marine-based activities,excursions, ecotours, sporting activities, personal training, and otherevents) with appropriate guides across varied fields of interest andvaried geographic regions (including outdoor activities and indooractivities). For example, users can identify, reserve, and pay foroutdoor opportunities that are offered by outdoor guides through acentralized computer system (e.g., server system, cloud-based computersystem), which can include connecting users with guides and outdooropportunities that are located near a user's current location or near alocation that the user will be visiting at a future date. Guides andguide opportunities can additionally and/or alternatively be identifiedbased on other search criteria (e.g., type of opportunity, date, time,guide reviews, guide ratings, required gear, price) that may beexplicitly and/or implicitly determined based on user input through aclient device, such as a mobile device (e.g., smartphone, tabletcomputing device), laptop, and/or desktop computer.

In some implementations, specifically programmed mobile applications(e.g., accessed via a smartphone or tablet) and web applications (e.g.,accessed via a browser of a computing device) to communicate with such acentralized computer system can be provided to, installed on, andexecuted/interpreted by client computing devices used by guides andusers. Mobile applications (referred to herein as “mobile apps”) and webapplications can provide features to generate, identify, reserve, andprocess payments for outdoor adventures or other activities (e.g.,trips, outdoor experiences) through, for example, securely accessingspecific hardware components on the client computing devices, likelocation services (e.g., global positioning system (GPS) components,Wi-Fi positioning components, wireless beacons), audio and visual inputs(e.g., cameras, microphones), volatile and non-volatile storagelocations (e.g., local storage devices, memory), output mechanisms(e.g., touchscreen display, speaker), and/or input mechanisms (e.g.,touchscreen, buttons, motion/orientation sensors). For example, a mobileapp that is installed on a guide's computing device can include inputfeatures through which a guide can geotag one or more locations that arerelevant to a proposed guide trip (e.g., meetup location, route to betravelled on the trip, recommended gear retailer location), select ortake photos/videos that depict the experience for a trip, inputequipment information and images (e.g., identifying what equipment isprovided by the guide or what equipment is recommend to be brought bythe user), and/or access a local calendar on the guide's device toidentify possible times for the guide trip. In another example, a mobileapp installed on a user's device, which may be the same as or differentfrom a mobile app installed on a guide's device, can include inputfeatures through which a user can provide permission for the currentgeolocation of the mobile device to be provided to and used by thecentralized computer system to identify nearby guided adventures,designate particular types of outdoor adventures (e.g., trips, outdoorexperiences) that are of interest, and/or select and secure registrationfor particular adventures. Additional and/or alternative mobile appfeatures are also possible.

In some implementations, a mobile app installed on a guide's computingdevice can provide an “on-duty” service in which the guide can activatean adventure opportunity when the guide is physically at the locationfor an adventure, which can prompt the centralized computer system topromote and book the adventure opportunity for nearby participants. The“on demand” service can be different from other adventure bookings thatare made further in advance of the adventure date/time, and which canhave attached cancellation policies (e.g., 24 hour cancellation policy).For example, a guide providing ski lessons can simply show up to a skiarea and activate the on-duty feature for a ski lesson adventure at theski area, and the central computer system can promote and book the skiadventure for nearby participants. The central computer system canpromote on-duty adventures in any of a variety of ways, such as throughproviding notifications (e.g., push notifications) on mobile apps ofusers who are currently (or were recently, historically) located nearthe location of the on-duty adventure, interested in that type ofadventure (e.g., based on express interests, based on historicaladventure participation), and/or combinations of other factors.Additionally and/or alternatively, the mobile device and app of theguide providing the on-duty adventure service can locally broadcastinformation about the on-duty adventure, such as through transmitting alocal beacon signal (e.g., BLUETOOTH low energy (BLE) beacon signal,Wi-Fi beacon signal, near filed communication (NFC) beacon) for whichuser mobile applications are programmed to listen, detect, and requestadditional information. Such beacon signals can include a uniqueidentifier for the on-duty adventure, which may be encoded with somehigher-level adventure type information (e.g., skiing type adventure,hunting type adventure, snow mobile type adventure) and which can beused by user devices to request additional information for and to bookthe adventure through the centralized computer system.

In some implementations, such a centralized computer system can serveadventure and guide information to user computing devices (e.g.,adventure description and images, guide reviews, required gear andlicenses), but can hold back some information relevant to the adventureuntil the adventure has been booked and/or proceeded until acancellation window has closed. Hold-back information can includeinformation that a user would be able to use in order to circumvent thecentralized computer system to book the adventure, such as the guide'sdirect contact information (e.g., phone number, email address), thespecific locations where the guide is scheduled to meet participants foradventures (e.g., street address for meet-up location), and/or otherdetails that users could potentially use to thwart the system.Similarly, information on participants in an adventure may be held backfrom guides until an adventure has been booked and/or has proceeded pastthe cancellation window.

In one implementation, a system for broadcasting on-duty adventureopportunities among computing devices includes an adventure managementcomputer system to manage information and reservations for adventureopportunities, the adventure management computer system including: afrontend (i) to receive requests to activate on-duty adventureopportunities and (ii) to transmit (a) push notifications to selectedmobile computing devices related to activated on-duty adventureopportunities and (b) local beacon signal identifiers formobile-to-mobile beacon signal transmissions for the activated on-dutyadventure opportunities, a backend (i) to select the mobile computingfrom among a group of mobile computing devices based, at least in part,proximity of the mobile computing devices to the on-duty adventureopportunities and (ii) to generate the local beacon signal identifiers,and a data storage system to store user data and adventure dataaccording to a particular database schema, wherein the user dataincludes, at least, location information for users associated with thegroup of mobile computing devices, wherein the adventure data includes,at least, (i) adventure information and (ii) the local beacon signalidentifiers. The system can further include a guide mobile computingdevice to activate an on-duty adventure opportunity and to locallybroadcast information for the on-duty adventure opportunity, the guidemobile computing device including: a display to output user interfacecontrol features for activating the on-duty adventure opportunity, aninput subsystem to receive user input activating the on-duty adventureopportunity, a location subsystem to determine a current location of theguide computing device, a first wireless communication chipset (i) totransmit a request to activate the on-duty adventure opportunity to theadventure management computer system and (ii) to receive a local beaconsignal identifier for the activated on-duty adventure opportunity, and asecond wireless communication chipset to transmit local beacon signalsfor detection by nearby mobile computing devices, the local beaconsignals including, at least, the local beacon signal identifier for theactivated on-duty adventure opportunity. The system can further includea participant mobile computing device (i) to detect the local beaconsignals with the local beacon signal identifier for the on-dutyadventure opportunity, (ii) to obtain the adventure information for theon-duty adventure opportunity from the adventure management computersystem, and (iii) to reserve the on-duty adventure opportunity with theadventure management computer system, the participant mobile computingdevice including: a first wireless communication chipset to detect thelocal beacon signals with the local beacon signal identifier for theon-duty adventure opportunity, and a second wireless communicationchipset to transmit a request for the adventure information for theon-duty adventure opportunity and to transmit a request to reserve theon-duty adventure opportunity.

Such an implementation can optionally include one or more of thefollowing features. The first wireless communication chipset of theguide mobile computing device can be a mobile data network chipset. Thesecond wireless communication chipset of the guide mobile computingdevice can be a Wi-Fi chipset. The second wireless communication chipsetof the participant mobile computing device can be a Wi-Fi chipset. Thefirst wireless communication chipset of the guide mobile computingdevice can be a mobile data network chipset. The second wirelesscommunication chipset of the guide mobile computing device can be aBLUETOOTH chipset. The second wireless communication chipset of theparticipant mobile computing device can be a BLUETOOTH chipset. Thefirst wireless communication chipset of the guide mobile computingdevice can be a Wi-Fi chipset. The second wireless communication chipsetof the guide mobile computing device can be a BLUETOOTH chipset. Thesecond wireless communication chipset of the participant mobilecomputing device can be a BLUETOOTH chipset. The activated on-dutyadventure opportunity can be reserved by the participant mobilecomputing device based on the local beacon signals from the guide mobilecomputing device being detected and without the participant mobilecomputing device needing to determine its own location. The locationsubsystem can include a global positioning system (GPS) subsystem todetermine the current location based on one or more detected satellitesignals. The location subsystem can include a local positioningsubsystem using terrestrial wireless signals to determine the currentlocation. The database schema can include a plurality of relationaldatabase tables that include, at least, (i) a booking table thatrepresents adventure reservation instances that each include a number ofreserved spots and (ii) a tour table that represents adventureopportunity instances that each include an aggregate number of remainingspots available. The aggregate number of remaining spots in the tourtable can be (i) redundant of an aggregation of the adventurereservation instances and (ii) provides a faster recall of the aggregatenumber of remaining spots from the database than the aggregation ofvalues in the booking table.

In another implementation, a method for broadcasting on-duty adventureopportunities among computing devices includes receiving, via a userinterface on a mobile computing device, user input to activate anon-duty adventure opportunity; obtaining, from a location subsystem ofthe mobile computing device, a current location of the mobile computingdevice; transmitting, using a first wireless chipset of the mobilecomputing device, a request to an adventure management computer systemfor activating the on-duty adventure opportunity, wherein the requestincludes, at least, the current location; receiving, using the firstwireless chipset of the mobile computing device, confirmation that thaton-duty adventure opportunity has been activated and an identifier forthe activated on-duty adventure opportunity; repeatedly transmitting,using a second wireless chipset of the mobile computing device, a beaconsignal that includes, at least, the identifier for the activated on-dutyadventure opportunity in the payload, wherein the beacon signal isformatted to be detected by another mobile computing device that, upondetection, will automatically cause the other mobile computing device torequest adventure information from the adventure management computersystem and to present an interface with reservation control features forthe on-duty adventure opportunity; receiving, using the first wirelesschipset of the mobile computing device, confirmation that the othermobile computing device has reserved the on-duty adventure opportunity;and stopping, by the mobile computing device, the repeated transmissionof the beacon signal in response to receiving the confirmation.

Such an implementation can optionally include one or more of thefollowing features. The first wireless communication chipset of themobile computing device can be a mobile data network chipset. The secondwireless communication chipset of the mobile computing device can be aWi-Fi chipset. The first wireless communication chipset of the mobilecomputing device can be a mobile data network chipset. The secondwireless communication chipset of the mobile computing device can be aBLUETOOTH chipset. The first wireless communication chipset of themobile computing device can be a Wi-Fi chipset. The second wirelesscommunication chipset of the mobile computing device can be a BLUETOOTHchipset. The activated on-duty adventure opportunity can be reserved bythe other mobile computing device based on the beacon signals from themobile computing device being detected and without the other mobilecomputing device needing to determine its own location. The confirmationcan include contact information for a user associated with the othermobile computing device that, prior to the on-duty adventure opportunitybeing reserved, was not available on the mobile computing device.Contact information for a user of the mobile computing device can betransmitted to the other computing device with confirmation of thereservation.

In another implementation, a method for on-boarding users to anadventure management platform includes outputting, on a computingdevice, a sequence of screens that each include one or more fields toenroll a user with the adventure management platform, wherein theadventure management platform provides electronic listings of outdooradventure opportunities that are available for reservation on a singlesite across a plurality of different adventure providers, wherein thesequence of screens comprises less than a threshold number of screens;receiving, at the computing device, user input via the sequence ofscreens to create an account for a user of the computing device;transmitting, by the computing device, the user input to an adventuremanagement computer system hosting the adventure management platform;receiving, at the computing device, confirmation that the account forthe user has been created; and accessing, on the computing device, theadventure management platform in response to receiving the confirmation.

Such an implementation can optionally include one or more of thefollowing. The sequence of screens can include a first screen thatobtains authorization to access data from one or more social mediaprofiles for the user, one or more second screens that are limited torequesting information that was otherwise not identified in the dataaccessed from the one or more social media profiles. The user includes aparticipant on the adventure management platform, and the thresholdnumber of screens is three screens. The user includes a guide on theadventure management platform, and the threshold number of screens isnine screens. The sequence of screens can include a first set of screensto create the account for the user and a second set of screens to createan initial adventure opportunity for the guide on the adventuremanagement platform.

In another implementation, a method for limiting access to guide andparticipant contact information on an adventure management platformincludes receiving, at an adventure management computer system hostingthe adventure management platform, a request to add an adventureopportunity to the adventure management platform, the request being froma guide computing device and including information identifying a guidefor the adventure opportunity; storing, by the adventure managementcomputer system, the adventure opportunity in association with anaccount for the guide on the adventure management platform, the accountincluding contact information for the guide; transmitting, by theadventure management computer system, information for the adventureopportunity to a participant computing device, wherein the informationdescribes the adventure opportunity and the guide without including thecontact information for the guide; receiving, at the adventuremanagement computer system, a reservation request for the adventureopportunity from the participant computing device; reserving, by theadventure management computer system, one or more spots on the adventureopportunity in association with the participant computing device; andtransmitting, by the adventure management computer system, confirmationof the reservation and the contact information for the guide after theadventure opportunity is reserved, wherein transmitting the contactinformation permits a participating user of the participant computingdevice to contact the guide directly without the adventure managementcomputer system being included in the communication.

Such an implementation can optionally include one or more of thefollowing features. The contact information can be transmitted inresponse to the adventure opportunity being reserved. The contactinformation can be transmitted in response to a cancellation period forthe reservation expiring.

In another implementation, a method for providing on-duty adventureopportunities includes activating an on-duty adventure opportunity beingoffered at a location; transmitting, in response to the activating,information describing the on-duty adventure opportunity to computingdevices near the location; and booking the adventure opportunity for aparticular user in response to a booking request from a particularcomputing associated with the particular user.

In another implementation, a system for providing on-duty adventureopportunities includes one or more computing devices each with aprocessor and memory storing instructions that, when executed, cause theprocessor to: activate an on-duty adventure opportunity being offered ata location; transmit, in response to the activating, informationdescribing the on-duty adventure opportunity to computing devices nearthe location; and book the adventure opportunity for a particular userin response to a booking request from a particular computing associatedwith the particular user.

In another implementation, a system for providing on-duty adventureopportunities includes means for activating an on-duty adventureopportunity being offered at a location; means for transmitting, inresponse to the activating, information describing the on-duty adventureopportunity to computing devices near the location; and means forbooking the adventure opportunity for a particular user in response to abooking request from a particular computing associated with theparticular user.

In another implementation, a method for on-boarding users to anadventure management platform includes outputting less than a thresholdnumber of screens to enroll a user with the adventure managementplatform; transmitting enrollment input received via the screens to theadventure management platform; and accessing the adventure managementplatform in response to receiving confirmation the user has beenenrolled.

In another implementation, a system for on-boarding users to anadventure management platform includes one or more computing deviceseach with a processor and memory storing instructions that, whenexecuted, cause the processor to: output less than a threshold number ofscreens to enroll a user with the adventure management platform;transmit enrollment input received via the screens to the adventuremanagement platform; and access the adventure management platform inresponse to receiving confirmation the user has been enrolled.

In another implementation, a system for on-boarding users to anadventure management platform includes means for outputting less than athreshold number of screens to enroll a user with the adventuremanagement platform; means for transmitting enrollment input receivedvia the screens to the adventure management platform; and means foraccessing the adventure management platform in response to receivingconfirmation the user has been enrolled.

In another implementation, a method for limiting access to informationon an adventure management platform includes transmitting adventureopportunity information that describes an adventure opportunity and aguide without including the contact information for the guide; reservingone or more spots on the adventure opportunity; and transmittingconfirmation of the reservation and the contact information for theguide after the adventure opportunity is reserved.

In another implementation, a system for limiting access to informationon an adventure management platform includes one or more computingdevices each with a processor and memory storing instructions that, whenexecuted, cause the processor to: transmit adventure opportunityinformation that describes an adventure opportunity and a guide withoutincluding the contact information for the guide; reserve one or morespots on the adventure opportunity; and transmit confirmation of thereservation and the contact information for the guide after theadventure opportunity is reserved.

In another implementation, a system for limiting access to informationon an adventure management platform includes means for transmittingadventure opportunity information that describes an adventureopportunity and a guide without including the contact information forthe guide; means for reserving one or more spots on the adventureopportunity; and means for transmitting confirmation of the reservationand the contact information for the guide after the adventureopportunity is reserved.

Certain implementations of the improved system or method may provide oneor more advantages. For example, users and guides can be moreefficiently on-boarded through web and mobile applications running onuser computing devices, and through a centralized computer system (e.g.,cloud based computer system, server system). For instance, instead ofproviding interfaces that include multiple different pages of forms andfields through which users are requested to provide information, whichcan be difficult and onerous on the user depending on the type ofcomputing device that he/she is using (e.g., type-inputs can be moredifficult on touchscreen interfaces, particularly devices with smallerform factor touchscreen displays). To facilitate user experience andon-boarding, user interfaces are provided through web and mobile appsthat request minimal inputs from a user by obtaining information fromother sources (e.g., other social platforms and/or accounts authorizedby users) and/or postponing obtaining some information until a latertime. For example, the centralized computer system can be programmed toprompt user computing devices to request information from users at ametered pace over time (e.g., ask for one additional field of userinformation every month) to spread the profile creation process overtime.

In a further example, mobile apps and web applications can additionallybe programmed to minimize network traffic and, thus, improve theperformance of the client computing devices and centralized computersystem. For example, mobile apps and web applications running on clientcomputing devices can be programmed to delay transmission of aguide/adventure search query until all parameters have been provided bya user so that intermediate results (e.g., results based on a portion ofthe parameters), which may only be partially relevant to the user, arenot served to the user, which could cause wasted/unwanted networktraffic. In another example, mobile apps and web applications can beprogrammed to cache guide and adventure information transmitted by acentralized computer system for at least a threshold period of time(e.g., 1 week, 1 month, 3 months, 1 year) and to reference the cachebefore requesting files and other data from the centralized computersystem so as to avoid retransmission of information already contained onclient computing devices. In another example, a centralized computersystem and client computing devices can be programmed to use one or moredata compression protocols that are common to across the centralizedcomputer system and client computing devices so as to minimize an amountof network traffic for the centralized computer system and clientcomputing devices to communicate.

In another example, the centralized computer system can be programmed touse a database schema that reduces latency associated with databaserequests. For example, the centralized computer system can use adatabase schema that includes fields that store aggregate data valuesthat, conventionally, would be stored across multiple database records.For example, conventionally the status of availability for an adventureopportunity on a particular date may be determined by querying a tablestoring each booking for a unique identifier associated with theadventure opportunity, retrieving data values for those records (e.g.,retrieving a number of spots that have been reserved in each booking),aggregating them, and then comparing them to a number of spots for theadventure to determine whether the adventure is available. In contrast,the centralized computer system can be programmed to store and update atally of available slots for a particular adventure opportunity with thedatabase record for the adventure opportunity as bookings are made. Bydoing this, the status of the adventure can be recalled throughretrieval of the single database record, which can reduce diskreads/writes, comparison operations, and the overall number of queriesthat are run to achieve the results. Although such a configuration maypresent possible data integrity issues where the tally is adjustedinconsistently with the bookings, the centralized computer system canmaintain a record of bookings that are queried and compared periodically(e.g., during periods of low traffic) to the tally to confirm theintegrity of the tally database records.

In yet another example, mobile apps and web applications can beprogrammed to minimize the use of computing resources on clientcomputing devices, which can minimize power consumption, improveoperational efficiency, and overall improve the operation of clientcomputing devices. For example, mobile apps and web applications can beprogrammed identify and register event handlers for particular clientcomputing devices so that device components, like location services, areaccessed at particular times during operation of the mobile apps and webapplications instead of being continually polled. For instance, an eventhandler may be registered on a client computing device so that locationservices are only polled when a user has selected a button to identifyguides or outdoor adventures that are located near the client computingdevice's current location. For example, on-duty activity broadcastingand reservations via a centralized computer system and client computingdevices can allow for nearby, currently available adventureopportunities to be transmitted to, received by, and displayed on usercomputing devices. User computing device can be placed in an on-dutymode of operation in which they poll the centralized computer systemand/or guide computing devices transmitting beacon signals for on-dutyadventure services. Polling the centralized computer system can involvetransmitting the client computing device's current location (e.g., GPSlocation, nearby access point identifier) to the centralized computersystem, which can determine whether any nearby on-duty services areavailable and can transmit information on nearby on-duty services to theclient computing device. To conserve resources (e.g., battery, processorcycles), the client computing device can be intermittently poll thecentralized computer system (e.g., every 15 minutes, whenever the devicehas moved more than a threshold distance from its previous location).Similarly, the centralized computer system can be programmed to trackon-duty requests from client computing devices and, if authorized by thedevices' users, to provide push notifications of nearby on-duty serviceas they become available.

In another example, nearby on-duty services can be identified to usercomputing devices without the user computing devices having to determineits own location and without needing to poll the centralized computersystem for nearby on-duty services. Instead, guide computing devices canbe programmed to enter into an on-duty broadcast mode in which theyactively transmit local wireless beacon signals (e.g., BLE beaconsignals, Wi-Fi beacon signals) with specialized headers and payloadsthat identify the beacon signals as on-duty activity advertisements.Additionally, the beacon signals can include payloads that includeunique adventure identifiers (e.g., uniform resource locators (URLs),unique identifier on the centralized computer system, universally uniqueidentifiers (UUIDs)) that the user computing devices can receive via abeacon signal, can use to obtain additional information on theadvertised adventure from the centralized computer system, and can useto book the advertised adventure. By using local beacon signals, a usercomputing device can passively monitor for beacon signals and, whenappropriate, request additional information from the centralizedcomputer system when a beacon signal is detected, instead of having toexpend the additional resources to determine its own location and thenperiodically poll the centralized computer system for nearby on-dutyadventures.

In yet another example, some guide-related information, such as contactinformation for guides, can be withheld from users until they havebooked an adventure and/or crossed a cancellation policy threshold. Suchfeatures can permit for the centralized computer system to act as acentral hub for adventure bookings, reviews, and processing, which canbuild a critical mass of both guides and users.

The details of one or more embodiments are set forth in the accompanyingdrawings and the description below. Other features and advantages willbe apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIGS. 1A-B are diagrams of example activity-sourcing computer systems.

FIG. 2 depicts an example database schema that can be used by anadventure management computer system.

FIG. 3 is a conceptual diagram of an example system for efficientlyon-boarding a user and/or guide to an adventure management computersystem.

FIGS. 4A-S are a set of example screenshots for on-boarding a guide toan adventure management platform.

FIG. 5 is a flowchart of an example technique for on-boarding a user onan example adventure management platform provided via an adventuremanagement computer system.

FIG. 6 is a conceptual diagram of an example system for restrictingaccess to guide and participant information on an example adventuremanagement platform.

FIGS. 7A-O are a set of example screenshots for restricting access toguide information until an adventure has been booked by a user on anadventure management platform.

FIG. 8 is a flowchart of an example technique for restricting access toparticipant and/or guide information until an adventure has been booked.

FIG. 9 is a conceptual diagram of an example system for providingon-duty adventure services.

FIG. 10 is a conceptual diagram of a system for local adventure beaconsignal transmissions.

FIG. 11 is a flowchart of an example technique for providing on-dutyadventure broadcasting and booking.

FIGS. 12A-M are a set of example screenshots for on-boarding a guide toan adventure management platform through an interface on a mobiledevice.

FIG. 13 is a block diagram of example computing devices.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIGS. 1A-B are diagrams of example activity-sourcing computer systems100 and 150 that provide platforms for connecting users with sources ofoutdoor adventure opportunities or other activities. In particularembodiments, the improved platforms can be implemented in a manner thatprovides guide-pairing computer system configured to pair users seekinga guided adventure, an outdoor activity, a lesson/tour, or otheractivity (e.g., either a specific, predetermined activity or aspontaneous, previously unplanned or unknown activity) with a variety offiltered sources for such users.

Referring to FIG. 1A, the example system 100 includes an adventuremanagement computer system 102 that can act as a centralized computersystem to facilitate connections between activity sources/providers(such as guides in this example) using activity-sourcing computingdevices 104 (referred to as guide computing devices 104 in this example)and users employing user computing devices 106.

The computer system 102 can include one or more computing devices, suchas a computer server, a desktop computer, a laptop computer, and/orother specially programmed computing devices. For example, the computersystem 102 can be a server system and/or a cloud-based computer system.The computer system 102 is programmed to provide a centralized systemthrough which activity sources/providers (such as guides in thisexample) can register, post proposed outdoor adventures outdoorexperiences/trips), receive payments, distribute summaries and media foroutdoor adventures to users, and manage user reviews/ratings; andthrough which users can register, identify and register for particularadventures that are of interest, submit payments for outdoor adventures,provide reviews/ratings, and/or share and receive media and otherinformation related to adventures. Other features are also possible withthe computer system 102.

The guide computing devices 104 and the user computing devices 106 canbe any of a variety of computing devices that are used by guides andusers, respectively. For example, the computing devices 104-106 can bemobile computing devices, peripheral computing devices (e.g., wearablecomputing devices, virtual reality headsets), laptop computers, desktopcomputers, and/or other types of computing devices. Guides and users caneach be associated with one or more of the computing devices 104-106.The computing devices 104-106 can communicate with the computer system102 using code that is installed, executed, and/or interpreted on thecomputing devices 104-106, such as mobile apps, web applicationsdownloaded and run in a web browser application, and/or otherapplications. The guide computing devices 104 can run the same ordifferent applications/code from the applications/code that is run onthe user computing devices 106. For example, the guide computing devices104 may download a guide-specific mobile app from the computer system102 (and/or from a separate computer system, such as a computer systemproviding a mobile app store) and the user computing devices 106 maydownload a different user mobile app. In another example, the guidecomputing devices 104 and user computing devices 106 may download thesame mobile app, but access different features that are part of themobile app once logged-in to the mobile app as either a guide or a user.

The computer system 102 and the computing devices 104-106 cancommunicate over one or more networks 108, such as the internet, localarea networks (LAN), wide area networks (WAN), virtual private networks(VPN), wireless networks (e.g., Wi-Fi networks, BLUETOOTH networks),wired networks, fiber optic networks, mobile data networks (e.g., 4Gnetworks), or any combination thereof. The computer system 102 and/orthe computing devices 104-106 may be bandwidth/data constrained by theirrespective internet service providers (ISP), so the computer system 102and/or the computing devices 104-106 can be programmed to use any of avariety of particular techniques to minimize and make networktransmissions more efficient as part of the system 100, such as throughcaching and/or data compression techniques.

The computer system 102 can include components that are specificallyprogrammed to interface with the guide computing devices 104 and usercomputing devices 106 to manage and serve requests for each of thesetypes of devices. For example, the computer system 102 includes a guidesubsystem 110 with a guide frontend 112 and a guide backend 114 that areprogrammed to process requests from the guide computing devices 104. Forexample, the guide computing devices 104 can transmit requests toregister, post proposed outdoor adventures, receive payments, distributesummaries and media for adventures to users, and manage userreviews/ratings over the network 108 to the computer system 102. Theserequests can be directed to the frontend 112 of the guide subsystem 110(e.g., addressed to a URL associated with the guide subsystem 110,transmitted to a port of the computer system 102 associated with theguide subsystem 110, include a parameter or other identifier associatedwith the guide subsystem 110), which can invoke one or more portions ofthe guide backend 114 to determine and process the requests. Responsesdetermined by the guide backend 114 can be served back to the guidecomputing devices 104 by the frontend 112 over the network 108.Additionally, in particular instances, the guide backend 114 cantransmit information and/or commands to the user subsystem 116, such asproviding guide's response to a user's message.

Similarly, the example computer system 102 includes a user subsystem 116with a frontend 118 and a backend 120 that are programmed to processrequests from the user computing devices 106. For example, usercomputing devices 106 can transmit requests to locate particular outdoorguided opportunities, such as searching based on the type of opportunity(e.g., hiking, fishing, hunting), geographic location or region (e.g.,city, state, zip code, user-designated geographic region, proximity tothe user's current location), availability at one or more dates andtimes (e.g., specific day and time, range of dates), user-generatedreviews or ratings (e.g., reviews and/or ratings from users whopreviously used a particular guide and/or particular trip), gearrequirements (e.g., list of gear that is needed to participate in aparticular trip), referrals or recommendations from other users (e.g.,recommendations from friends), price (e.g., cost to participate in aguided trip), and/or other fields/information to identify particularguided opportunities. Such requests can be directed to the frontend 118of the user subsystem 116 (e.g., addressed to a URL associated with theuser subsystem 116, transmitted to a port of the computer system 102associated with the user subsystem 116, include a parameter or otheridentifier associated with the user subsystem 116), which can invoke oneor more portions of the user backend 120 to determine and process therequests. Responses determined by the user backend 120 can be servedback to the user computing devices 106 by the frontend 118 over thenetwork 108. Additionally, in particular instances, the user backend 116can transmit information and/or commands to the guide subsystem 110,such as providing information confirming a user's reservation for anadventure opportunity posted by a guide through the guide subsystem 110.

The computer system 102 accesses and uses a data repository 122 to storeinformation for providing location-based outdoor guide and outdooradventure services for users and guides. The data repository 122 caninclude any of a variety of information, such as guide information(e.g., guide name, guide contact information, guide username andpassword, guide computing device identifier(s), guide skills andexperience, guide location(s), photos and videos of guides), userinformation (e.g., user name, user contact information, user usernameand password, user computing device identifier(s), user interests, usergear, user location(s)), adventure information (e.g., type of adventure,geo-tagged locations for the adventure, date and time, duration,required gear, recommended commercial gear to purchase for theadventure, skills/experience needed for adventure, skills/experience tobe gained, example photos and summaries from similar adventures,reviews/ratings for the adventure), and/or media (e.g., adventure photosand videos shared with users). Other information is also possible.

The data repository 122 can include one or more data schemas that areused for organizing and storing data in a manner that can providereliable and efficient information retrieval. For example, as describedbelow in more detail with regard to FIG. 2, the data repository 122 caninclude various tables and data fields that can minimize querying anddata record retrieval during run time of the adventure managementcomputer system 102 in serving requests from the user computing devices106 and/or the guide computing devices 104. Additionally, the adventuremanagement computer system 102 can restrict access to particular userand/or guide information stored in the repository 122 to appropriatetimes during an adventure-booking process. For example, the usercomputing devices 106 may not receive guide contact information (e.g.,email, phone number) until an adventure for a guide has been bookedand/or proceeded past a cancelation period. Such features can preserveuser privacy and can also ensure that the adventure management computersystem 102 serves as a central hub of adventure related interactionsamong guides and users.

The adventure management computer system 102 can additionally facilitateon-duty adventure bookings between the user computing devices 106 andthe guide computing devices 104. For example, guide computing devices104 can activate on-duty adventures at various points in time via theguide subsystem 110 and the data repository 122, which can causeinformation on the on-duty adventures to be transmitted to the usercomputing devices 106 via the user subsystem 116.

The example system 100 additionally includes other computer systems 124,such as social media computer systems hosting social media platforms,merchant computer systems hosting merchant sites, and/or other systems.The other computing systems 124 can be used and accessed in any of avariety of ways. For example, the other computing systems 124 andinclude social media computer systems can be used to provide logincredentials for the adventure management computer system 102 and toobtain baseline user information to facilitate both user and guideon-boarding. In another example, the other computing systems 124 caninclude merchant computer systems that can be linked to by URLs includedin content provided to the user computing devices 106. The URLs can linkto web pages (or other online-accessible interfaces) for products thatare recommended by guides, such as products includes in a gear kit thata guide recommends for a particular outdoor adventure.

While this document describes examples of activity sources/providers asguides, other activity source/providers are also possible with thedisclosed technology, such as people and/or entities providing any of avariety of services, such experts providing demonstrations, instructorsproviding lessons, equipment owners/managers providing equipment/gearfor use/rental, property/facility owners/managers providing use of aproperty (e.g., building, land, sports field), and/or other appropriateservices. Similarly, guide services and outdoor activities are providedas examples of available activities, and other activities are alsopossible with the disclosed technology, such as equipment use/rental,property use/rental, instructions, lessons, demonstrations, professionalservices, and/or other activities. Additionally, guide computing devicesare examples of activity-source computing devices and other types ofactivity-source computing devices are also possible with the disclosedtechnology, such as computing devices used by experts, instructors,equipment owners/managers, property owners/managers, and/or other peopleand/or entities. The disclosed technology (as described throughout thisdocument) can be extended and/or adapted to other activitysources/providers, other available activities, and/or otheractivity-source computing devices not explicitly described in theexamples in this document.

Referring to FIG. 1B, the system 150 includes a cloud-based serversystem 152 that interfaces with an example mobile computing device 172and an example desktop computing device 174. The cloud-based serversystem 152 is an example implementation of the adventure managementcomputer system 102 described above with regard to FIG. 1A. The examplecomputing devices 172 and 174 are examples of the guide computing device104 and/or the user computing devices 106.

The cloud-based server system 152 includes a load balancer 164, anextensible and scalable web server group 160 (e.g., AMAZON ElasticCompute Cloud (Amazon EC2)), an extensible and scalable app server group162 (e.g., AMAZON EC2), an extensible and scalable cache group 154(e.g., AMAZON ElastiCache), a cloud storage service 158 (e.g., AMAZONSimple Storage Service (S3)), a backend server 156, and underlying datastorage systems 166-168. The cloud-based server system 152 can providethe adventure management features described above with regard to FIG. 1A(and throughout the rest of this document) in an extensible and scalablemanner so that the system 152 is able to handle spikes and variation intraffic and performance. Other implementations of the adventuremanagement computer system 102 are also possible.

FIG. 2 depicts an example database schema 200 that can be used by anadventure management computer system to provide reliable and efficientdata storage and retrieval. The example database schema 200 can be used,for example, to store information in the data repository 122, the cloudstorage service 158, and/or the underlying data storage system 166-168.Storing data in any of the data storage systems using the schema 200 canpermit for low latency data retrieval based on minimizing the number ofqueries, read operations, and comparison operations that are performedto obtain and serve the relevant data.

For example, the adventure management computer system 102 can frequentlymake calls to the data repository 122 for adventure opportunities thathave availability for user participation when serving information onavailable opportunities to user computing devices. Such dynamicallychanging and frequently used data can be optimized, for example, usingthe data schema 200 by including a data record for the current number ofremaining slots in an adventure opportunity, instead of having todynamically recreate that value from records of adventure bookings(conventional approach). The adventure management computer system 102can be programmed to automatically update and ensure the accuracy ofdata records identifying the number of remaining slots. Additionaland/or alternative data elements that dynamically change can beoptimized for efficiency in the schema 200 as well.

In the example schema 200, a users table 202 includes a variety of datafields pertaining to users of the adventure management computer system102, such as name, username, password, contact information (e.g., phone,email), and other pertinent details. The table 202 can be used for bothguides and adventure participants (also referred to as users), which canprovide for simplicity and can allow for guides and participants tochange roles seamlessly (e.g., some guides may participate in otheradventures). To provide for efficient and streamlined on-boarding ofusers, the adventure management computer system 102 can allow for auser's record to be created in the table 202 with some of the fieldsmissing, which may be filled out at later date.

A flow_user_progress table 204 can be used to store user progress acrossa number of different process flows, including profilecreation/modification, adventure opportunity creation/modification,adventure booking, and/or other flows that may be used throughout theadventure management computer system 102. Each of the process flows canbe stored in the flow table 206, which can be enumerated by one or moresteps that are stored in the flow_step 208 table.

Integration with user accounts on other platforms, such as social mediaplatforms (e.g., FACEBOOK, TWITTER, INSTAGRAM, SNAPCHAT), can be storedand maintained through the integration table 210. Such integrations andauthorizations with other platforms can assist with the on-boardingprocess by allowing the adventure management computer system 102 toobtain user data from these other sites without having to ask the userto enter them.

User logins and other recurring access to the site can be managedthrough the user_access_token table 212.

Properties can be designated through the properties table 214, whichincludes fields through which properties, such as adventures, adventurelocations, and combinations thereof, can be designated. The propertiestable 214 includes a property_uid field that uniquely identifies eachproperty, which can be referenced across other tables, such as thetour_proviles table 216 and the tours table 218 described below, whichdefine adventures being offered by guides and presented to users forreservation. For example, each tour and tour_profile can reference aproperty to which an adventure pertains, and each of the properties canbe referenced across multiple different adventures.

Each guide can create one or more adventure opportunities that arerepresented by data records in the tour_profiles table 216, which canspecify the following information for an adventure: title, description,day of week, price (kids, adults), spaces (kids, adults), an indicationof whether it is repeating, start and end dates if it is repeating,duration, and other information.

The tour_profiles table 216 can store templates that are used to definespecific adventure opportunity instances that are stored in the tourstable 218, which can include much of the same information as in thetour_profiles table 216 as well as a specific date for each adventure, arunning tally of the spaces available on the adventure, and otherdetails. By duplicating some details from the tour_profiles table 216into the tours table 218, the adventure management computer system 102can reduce the number of queries and comparisons that are performed bysimply needing to retrieve a record from the tours table 218 instead ofadditionally having to retrieve a record from the tour_profiles table216. Such minimization of table queries can improve efficiency andreduce latency when serving requests. Additionally, the running tally ofspaces available in the tours table 218 can reduce latency by avoidingcalls to other tables to dynamically determine the availability.

Bookings for tours by users can be represented by the booking table 220,which can indicate the adventure (event_time_id) that the bookingpertains to, the user who make the booking, the number of spots beingbooked, the price, the current step in the booking process, and otherdetails. Each booking can have one or more items that are stored in thebooking_item table 222, which can list the components of the booking.

Collections of adventures can be designated via the collection_advntrtable 226 and the collection table 228. The collection table 228 candefine adventure collections, including a collection title, description,image, and unique collection identifier. Individual adventures can beadded to specific collections via the collection_advntr table 226, whichcan include entries cross-referencing collection identifiers andadventure identifiers.

FIG. 3 is a conceptual diagram of an example system 300 for efficientlyon-boarding a user and/or guide to an adventure management computersystem 302. The adventure management computer system 302 can be similarto the adventure management computer system 102 described above withregard to FIG. 1A. In the depicted example, a user computing device 304(similar to the computing devices 104-106) is progressing through anonboarding process for users and/or guides. The adventure managementcomputer system 302 can maintain a user database 308 (e.g., using thedatabase schema 200), which can be populated, at least in part, withinformation from a social media system 306 (example of other computersystems 124).

As indicated by step A (312), an onboarding process is started on theuser computing device 304 (example flow from the flow table 206). Aspart of the onboarding process, the user computing device 304 can obtainsocial media authorization for the adventure management client device onthe user computing device 304 and/or the adventure management computersystem 302 to obtain access so social media data for the user, which canbe stored locally on the user computing device 304 and/or remotely onthe social media system 306, such as in the social media user datarepository 310. As an example of this first portion of the onboardingprocess, the user computing device 304 can transmit social mediaauthorization to the adventure management computer system 302 (step B,314), which can authorize access to the user data with the social datawith the social media system 306 (step C, 316). Once authorized, thesocial media system 306 can provide the social media data to theadventure management computer system 302 (step D, 318), which can relaythe social media data back to the user computing device 304 (step E,320). Alternatively and/or additionally, the user computing device 304can locally retrieve social media data from the device 304 using theauthorization.

Once the user computing device 304 has the social media data, the usercomputing device 304 can populate fields of for the onboarding processfrom the social media data (324). By doing this as an initial step, theuser computing device 304 can attempt to fill as many fields as possiblefor the user with readily accessible social media data rather thanasking the user to provide that information another time. For example,the user computing device 304 can populate name, email address,location, and/or other information that a user may have provided as partof his/her social media account. The user computing device 304 can usevarious mappings to correlate the social media data to appropriatefields for the adventure management computer system 302.

With the social media data populating fields, the user computing devicecan request minimal other user data (326). For example, with a useraccount, the user computing device 304 may not request any additionalinformation from the user after the social media data has been populatedinto the fields. With a guide, the user computing device 304 mayregister the guide as a user initially and then request that the guideenter in an initial adventure via the system. Either way, the usercomputing device 304 can request a minimal amount of data from the user,which can streamline the on-boarding process.

The data entered by the user can be uploaded in an ongoing or bulkfashion, as indicated by step F (328). The adventure management computersystem 302 can store the data according to the data schema for thedatabase 308, as indicated by step G (330). Once the user has beenon-boarded, the user can be provide with access to the site, asindicated by step H (332).

FIGS. 4A-S are a set of example screenshots for on-boarding a guide toan adventure management platform, such as the adventure managementcomputer system 102 and/or 302. The example GUIs can be provided onexample guide computing devices, such as the guide computing devices104. The depicted GUIs are example web applications that can be providedthrough web browsers (e.g., GOOGLE CHROME, SAFARI, INTERNET EXPLORER)being executed on, for example, the guide computing devices 104 usingweb pages downloaded from the computer system 102 over the network 108.The example web pages can include one or more types of code (e.g.,markup code, scripts) that are executed/interpreted by the guidecomputing devices 104 to provide an interactive web application on theguide computing devices 104 through synchronous and/or asynchronousrequests transmitted to the computer system 102 over the network 108.Although the example GUIs depicted in FIGS. 4A-S are depicted as webapplications, they can additionally and/or alternatively be implementedin other formats, such as for mobile apps specifically programmed forone or more mobile computing devices (e.g., IOS smartphones, ANDROIDsmartphones, tablet computing devices).

Referring to FIG. 4A, a first example GUI 400 through which a guide caninitially register with an adventure management computer system (e.g.,the computer system 102) is depicted. In this example, the guide isprovided with a number of selectable buttons 402, 404 through which theguide can initiate the on-boarding process. The GUI 400 also providesother navigational links through which the user can access otherfeatures, such as the “Adventures” link to access, search for, andreserve adventures, the “Become A Guide” link to access informationdescribing the process and conditions for becoming a guide, and the“Sign In” link for users who have previously created an account tologin. Referring now to FIG. 4B, in response to selecting one of theselectable buttons 402, 404, the guide can be provided with a prompt 408to continue the login using credentials for an example social mediaplatform (FACEBOOK). The prompt 408 can include an option to opt-in tothe terms and conditions for using the site, which can be presented tothe user in their entirety by selecting the “Terms and Conditions” link.Referring now to FIG. 4C, in response to selecting the “continue” buttonin the prompt 408 (and opting into the terms and conditions), the guidecan be presented with information 410 describing the implications ofcontinuing to login via the social media account (e.g., providing theadventure management computer system with information from the guide'spublic profile and email address) and the option to consent to theauthorization.

In response to authorizing the adventure management computer system toaccess the social media information, that social data for the guide canbe retrieved and used to populate an initial form 412 with fields414-420 for the guide's profile, as depicted in FIG. 4D. In thisexample, the guide's name and contact information are prepopulated intothe fields 414 and 416. The other fields 418-420 would be populated aswell if the social data for the guide had included those details. Oncethe guide has entered sufficient information through the form 412, theguide can select the next button 422.

Referring now to FIG. 4E, the guide can be prompted to select/setprofile and cover photos (424) that have been populated from the socialmedia data for the guide, and can be asked to identify other socialmedia accounts that are associated with the user (426). These can beoptional fields that a user can fill out. Once ready, the guide canselect the finish button 428.

Referring now to FIG. 4F, the guide can be prompted to create his/herfirst adventure listing, as indicated by the button 430. A user who isnot intending to initially act as a guide (but is not precluded fromdoing so at a later date) would not be presented with the option 430. Inresponse to selecting the button 430, a first step in creating anadventure listing (identified in the status bar 432 as “basics”) ispresented to the guide with fields 434-444, as depicted in FIG. 4G.Where possible, the fields 434-444 include shorter lists of enumeratedvalues that can be readily selected by a user, to simplify the guideon-boarding process. For example, the categories 436 can be enumeratedto a few high-level categories (e.g., bike, hike, hunt, fish, snow), theexperience level 440 can be enumerated as three categories (e.g.,beginner, intermediate, expert), and the cancellation policy can besimplified to a few categories of pre-determined cancellation policies(e.g., flexible, moderate, strict). The photos 444 can be selectablefrom any local and/or remote image source that is authorized for theuser of the device.

Referring now to FIG. 4H, example values and photos have been selectedfor each of the fields 434-444. In this example, a ski lesson adventureis being created by the guide. Additionally, example annotationsdescribing different cancellations policies are depicted in the popup448. Once ready, the guide can select the next button 446.

Referring now to FIG. 4I, additional details for the adventure arerequested via the fields 450-454. In this example, the guide hasprovided a description of the example adventure (450) and has identifiedwhat a user should bring (452). Once ready, the guide can proceed to thenext step by selectin the next button 456.

Referring now to FIG. 4J, location information for the adventure can beprovided via the fields 458-462. The location can either be designatedin the textual location fields 458 or through the interactive map 460.Once one is populated, the other can be determined and automaticallypopulated as well. The location can be the starting location whereparticipants are to meet the guide to participate in the adventure, withmore granular instructions on where to physically meet the guide whenthey arrive at the location. Once ready, the guide can select the nextbutton 464 to proceed to the next step.

Referring now to FIG. 4K, calendar information for the adventure can beprovided via the fields 466-480. In the depicted example, the guide isable to designate a starting date and time (466), a prices (468), amaximum group size (470), whether it is a repeating adventure (472), andif it is repeating, the frequency of repetition (476) and the end datefor the adventure (476). The pricing features 468 include, for example,selectable options to designate the pricing type (e.g., “per person”pricing type, “per group” pricing type) and a field to enter a price(e.g., $100) for the designated pricing type. In some implementations,prices can be entered and recorded for multiple pricing types, such asentering a first price for a per person pricing type and a second pricefor a per group pricing type. In such implementations, the guide maydesignate conditions under which one or both pricing types are providedand made available for reservation by users (e.g., guide can designatethat both options are concurrently available for reservation, guide candesignate that the per user option only becomes available forreservation when the per group option has not yet been reserved within athreshold time period of the adventure (e.g., not reserved within 1 weekof the adventure), guide can designate that the per group option onlybecomes available for reservation when the per person option has not yetbeen reserved within a threshold time period of the adventure (e.g., notreserved within 1 week of the adventure)). The calendar icon 478 aindicates a current day and the calendar icons 478 b indicate the datesfor the adventure as designated. Once ready, the user can select thesave or cancel button 480. Once saved, the user can enter another set ofcalendar dates for the same adventure, as indicated by FIG. 4L, whichdepicts the repeating dates designated in FIG. 4K (482) and a newoccurrence for the activity (478 c). Once ready, the user can select thenext button 484.

Referring to FIG. 4M, the user can then preview the adventure and, whenready, can select the finish button 486. Once uploaded and completed,the adventure may undergo automatic and/or human review before beingofficially approved and going live on the site.

Referring now to FIG. 4N, once the initial listing has been created, theguide can be prompted to setup a payment account so that he/she can beelectronically and automatically paid for his/her services. Selectingthe button 488 can initiate the account payment setup process, which canbe a single interface 490 provided by a third party and automaticallylinked to, as indicated by FIG. 4O.

Once the onboarding process (FIGS. 4A-O) for the guide has beencompleted, the guide can view a customized view of his/her account onthe site. Referring to FIG. 4P, a dashboard interface 492 can bepresented that includes a listing of all adventures that the guide hascreated along with statistics, revenue, and other information, alongwith a button to create another adventure.

Referring to FIG. 4Q, a passport interface 494 can be presented, whichprovides the guide with a list of adventures in which the guide has beena participant on another guide's adventure. The passport interface 494includes upcoming adventures (booked adventures) and a history ofadventures.

Referring now to FIG. 4R, a profile interface 496 can be presented tothe guide through which the guide can view his/her profile, associatedphotos and social media content, and reviews from past participants. Theguide can use the profile interface 496 to manage his/her publicimage/presentation to potential participants. Some of all of theinformation in the interface 496 can be accessible to the public.

Referring now to FIG. 4S, an account interface 498 can be presentedthrough which a guide can manage his/her account settings, which caninclude contact information, security, payment information, payouts, andverification features.

FIG. 5 is a flowchart of an example technique 500 for on-boarding a useron an example adventure management platform provided via an adventuremanagement computer system 502. The technique 500 can be performed,in-part, by the system 502 (similar to the systems 102, 302), a usercomputing device (similar to the computing devices 104-106, 304), and asocial media system 508 (similar to the other systems 124, 306).

The technique 500 include the computing device 504 initiating anon-boarding process (508), which includes obtaining social medialauthorization for the adventure management system to have access tosocial media data for the user (510). The computing device 504 canverify and/or record the authorization with the social media system 506(512), and, once verified, can obtain social media data for the user.The social media data can be obtained locally from the computing device504 and/or via communication with the social media system 506. Using thesocial media data, the user data for the on-boarding process can bepre-populated using the social media data (513) and the user can beprompted to provide the remaining user data in a threshold number of UIpages of less (514). For example, the non-guide onboarding processdepicted with regard to FIGS. 4A-E included two UI pages (FIGS. 4D and4E) once the social media authorization was obtained. For guideonboarding processes, the UI pages can include the two pages for useron-boarding (FIGS. 4D and 4E) as well as the five UI pages for creatingand approving an adventure listing (FIGS. 4G-M), and the one paymentaccount enrollment UI (FIG. 4O) —for eight UI pages from start to finishfor a guide to be up and running with a fully functional e-bookingsystem. Other configurations and UI arrangements are also possible. UIpages can include interfaces that present a limited amount ofinformation/fields that require navigation to another page to viewadditional information/fields.

Once the user data has been obtained, it can be uploaded to the system502 (516), which can store the user data (518) and activate the useraccount (520). The user device 504 can receive confirmation of theactivation (522). Once enrolled, the system 502 can also promote theuser and his/her adventures on the system 502 and on other authorizedsystems, such as the system 506 (524), which can present informationpromoting the user and/or his/her adventure listings (526).

FIG. 6 is a conceptual diagram of an example system 600 for restrictingaccess to guide and participant information on an example adventuremanagement platform 602. The adventure management platform 602 can besimilar to the adventure management computer systems 102, 302, and 502described above with regard to FIGS. 1A, 3, and 5. In the depictedexample, a participant computing device 606 (similar to the usercomputing devices 106) books an adventure with a guide associated withthe guide computing device 604 (similar to the guide computing devices104) and the adventure management computer system 602 restricts accessto some participant and guide information until the booking has beenconfirmed, has progressed past a point of cancellation, and/or otherfactors. The adventure management computer system 602 can maintain auser database 608 and an adventure database 610 (e.g., using thedatabase schema 200), which can store participant and guide information,such as contact information.

Referring to step A (612), the guide computing device 604 can create anadventure opportunity with the adventure management computer system 602,which can store the adventure opportunity in the adventure database 610(step B, 614). The participant computing device 606 can be served withadventure opportunities by the system 602 (step C, 616), which caninclude information describing the adventure opportunity created by theguide computing device 604. Such information may not include directcontact information for the guide computing device 604, such as theguide's email address, phone number, direct messaging user names, and/orother features through which the participant could directly contact theguide. In some implementations, the system 602 may permit communicationbetween the guide and the participant in advance of the adventure beingbooked by the participant so long as it flows through and is moderatedby the system 602 (step D, 618). Such moderation can include, forexample, human facilitators and/or automated bots that anonymize guideand participant identities, review the message for direct contactinformation, and/or other content filters.

As indicated by step E (620), the participant computing device 606 canbook the adventure with the system 602, which can store the adventurebooking in the database 610 (step F, 622). After the booking has beenstored, the system 602 can transmit a booking notification to the guidecomputing device 604 that can include previously restricted participantinformation 626 (step G, 624). Similarly, the system 620 can transmit abooking confirmation to the participant computing device 606 that caninclude previously restricted guide information 630 (e.g., email, phonenumber, other contact information). Using the previously restrictedinformation, the guide and the participant devices 604 and 606 can beput in direct communication with each other, as indicated by step I(632). In some implementations, such information 626 and 630 may not beprovided to the devices 604 and 606 until the booking has progressedbeyond a point of cancellation. Prior to the cancellation periodexpiring, the communication may need to flow through the system 602(step D, 618).

FIGS. 7A-O are a set of example screenshots for restricting access toguide information until an adventure has been booked by a user on anadventure management platform, such as the adventure management computersystem 102 and/or 302. The example GUIs can be provided on example guidecomputing devices, such as the user computing devices 106 and/or theparticipant computing device 606. Although the example GUIs are mobileapps specifically programmed for one or more mobile computing devices(e.g., 105 smartphones, ANDROID smartphones, tablet computing devices),they can additionally and/or alternatively be provided via otherinterfaces, such as through web browsers providing we applications.

Referring to FIG. 7A, an initial screen 700 is presented to a mobile appuser requesting that the user log in via a social media account (e.g.,FACEBOOK). In response to selecting the button, an on-boarding processfor the user can start similar to the one described above for guideswith regard to FIGS. 4A-E, as indicated by FIG. 7B and the screen 702.Once the onboarding process is complete (e.g., additional screens can bepresented similar to those in FIGS. 4A-E, the initial on-boardingprocess for the user may be limited to just the screen 702), the usercan be presented with the explore interface 706 through which the usercan be presented with a number of available adventures 710-714 that arerelevant to the user (e.g., relevant in terms of proximity to the user,interests of the user), as indicated by FIG. 7C. The adventures 710-714can be presented in the interface 106 with various information, such asimages depicting the adventure, a description of the adventure, alocation for the adventure, pricing for the adventure, a pricing typefor the adventure (e.g., per person pricing, per group pricing), and adistance from the user's current location (e.g., location determined forthe user's mobile device, such as a current location determined via GPSand/or Wi-Fi location processing). The adventures 710-714 can beautomatically ordered based on any of a variety of factors, such asbeing ordered based on proximity to the user's current location (e.g.,ordered from closest to furthest away adventure), a matching scoreindicating how well the adventure matches one or more search criteria(e.g., adventure type, price, schedule), and/or combinations thereof. Asearch interface 716 is also presented through which the user can searchfor adventures along one or more parameters (e.g., location, type ofadventure, duration, date, price, spots available). The user can toggleto different interfaces through the footer 708.

Referring to FIG. 7D, a discover interface 718 is presented thatincludes adventures presented in different categories 720-724 that theuser can select and explore in greater detail. Referring to FIG. 7E, anupcoming passport interface 726 (the “upcoming” tab selected) ispresented, which depicts upcoming/booked adventures for the user.Referring to FIG. 7F, a past passport interface 728 (the “past” tabselected) is presented, which depicts previous adventures 730 that theuser has taken. Referring to FIG. 7G, a profile interface 732 ispresented which includes information about the user, including profilestatus information 734 indicating what information has been provided tothe adventure management system for the user, such as the user's phonenumber, email, and social media accounts/feeds (e.g., TWITTER feed,INSTAGRAM feed). Referring to FIG. 7H, a listings interface 736 ispresented which provides a list of adventures 738 that the logged-inuser has created.

Referring to FIGS. 7I-J, in response to the user selecting the adventure710 for the “gravel bike adventure,” the interface 740 is presented,which includes detailed information on the adventure and features tobook the adventure. For example, the interface 740 includes a largerimage 742, a description of the adventure 744, location/duration/skilllevel information 746, date and time information 750, remaining spotsand price 752, a description 754, instructions on what to bring 756,licenses for the trip 758, and a button 748 to book the adventure. Asdepicted in the interface 740, contact information for the guide orother mechanisms through which the user could communicate directed withthe guide are not presented at this point in the booking process.Referring to FIG. 7K, the user selects the reservation button 752 andtoggles the reservation up to 2 spots, and selects the book button 748.

Referring to FIG. 7L, an interface 760 with a summary of the adventurebooking is presented with fields 762-774 summarizing various aspects ofthe reservation to be made. The user is presented with a radio button770 to agree to the licensing requirements (and other requirements) forthe adventure, and an option 772 is presented for providing a method ofpayment. Referring to FIG. 7M, an interface 778 to provide paymentinformation is presented in response to selection of the option 772. Theinterface 778 can include fields 780 and 782 through which the user canprovide contact and payment information, which were not required orcollected previously by the system during the on-boarding process butwhich can be added to the user's profile as they are collected.

Referring to FIG. 7N, after the payment information has been providedand the pay button 776 has been selected, confirmation of the bookingcan be provided to the user via the interface 784, which can include asummary of the reservation 762-768, 786 as well as previously restrictedinformation 788-790. In this example, the previously restrictedinformation includes the specific meetup location 788 and the guidecontact information 790. Referring to FIG. 7O, in response to theadventure being booked, the adventure can be presented in the upcomingpassport interface 726 so that the user can readily track his/herschedule.

FIG. 8 is a flowchart of an example technique 800 for restricting accessto participant and/or guide information until an adventure has beenbooked. The technique 800 can be performed, in-part, by an adventuremanagement system 802 (similar to the systems 102, 302, 502), a guidecomputing device 804 (similar to computing devices (similar to computingdevices 104, 304), and a participant computing device 806 (similar tothe computing devices 106, 304, 506).

The guide computing device 804 can create an adventure (808) that istransmitted to and stored by the system 802 (810). The system 802 cantransmit the adventure information to the participant computing device806 (812), which can display the adventure (814). The informationprovided to the participant computing device 806 can be restricted so asto not include any contact information for the guide or otherinformation that could be used to circumvent the system 802. Optionally,the participant computing device 806 can initiate communication with theguide (816, 820) via a pre-booking communication session managed andmonitored by the system 802 (810).

The participant device 806 can book the adventure with the system 802(822), which can store the adventure booking (824) and proceed toprovide booking confirmation (826). The booking confirmation can includethe participant information 828 being provided to the guide computingdevice 804, which can display the confirmation (830), and can includethe guide information 832 being provided to the participant computingdevice 805, which can display the booking confirmation (834). Using theguide and participant information (828, 832), the guide and participantcan engage in direct communication with each other (836, 838).

FIG. 9 is a conceptual diagram of an example system 900 for providingon-duty adventure services. The adventure management platform 902 can besimilar to the adventure management computer systems 102, 302, 502, 602,and 802 described above with regard to FIGS. 1A, 3, 5, 6, and 8. In thedepicted example, a guide computing device 904 (similar to the guidecomputing device 104) activates an on-duty adventure (which may havebeen previously created and permits the guide to activate/deactivate),which is broadcast to participant computing device 906 and 908 (similarto the user computing devices 106). The system 902 manages the bookingof the on-duty adventure using the adventure database 910 (e.g., usingthe database schema 200).

The guide computing device 904 can present an interface 912 for theguide to view, modify, and activate a previously created adventure sothat it is provided on-duty. For example, the guide can navigate to theinterface 736 to and can select an adventure to activate on-duty. Asdepicted in the example interface 912, the location field 914 for theadventure can be set to the current location of the guide computingdevice 904, the on-duty slider 916 can be set to “yes” (meaning that theadventure is being provided on-duty), and the activate button 918 can bepressed to activate the on-duty adventure. Activating the on-dutyfeature can cause the guide computing device 904 to locally broadcastthe adventure to other nearby devices and for the system 902 tobroadcast the adventure to participant computing devices that arelocated nearby and/or are interested in the adventure.

In response to the user selecting the activate button 918, the guidecomputing device 904 can transmit a request to activate the on-dutyadventure to the system 902 (step A, 920). In response to receiving theon-duty activation request, the system 902 can generate an identifierfor the adventure (step B, 922), which can be stored in the adventuredatabase 910 and transmitted back to the guide computing device 904(step C, 924-926). The identifier can uniquely identify the adventure onthe system 902 and/or universally (e.g., UUID, URL). The guide computingdevice 904 can locally broadcast the on-duty adventure by embedding theidentifier 926 in the local broadcast (step D, 928). For example, thedevice 904 can transmit a broadcast signal that includes the identifier932 in the payload of the broadcast signal (step E, 930). Such a signalcan be, for example, a beacon signal that can be passively monitored forand detected by other devices that are within a local broadcast range934 for the signal, such as the participant computing device 906 that islocated within the range 934. Any of a variety of appropriate wirelessprotocols and chipsets can be used for the broadcast signal 930, such asstandardized and widely adopted wireless protocols on mobile deviceslike BLE, Wi-Fi, and NFC. The range 934 can depend on the chipset andwireless protocol that is used for the broadcast signal. For example, ifthe broadcast signal is transmitted using the Wi-Fi standard andchipset, the local broadcast range 934 can be up to 30 m-40 m. Given thephysical limitations of local wireless broadcasts from the guidecomputing device 904, the guide may have the best success of his/herbroadcast being received by another user who is interested in an on-dutyadventure opportunity if the guide positions the device 904 in alocation with a larger group of people. For example, a guide offeringon-duty ski lessons may want to position himself/herself with the device904 in a crowded lodge, hotel, or ski lift at the ski area.Additionally, the guide computing device 904 can be programmed totransmit the broadcast signal over multiple different wireless protocols(e.g., both Wi-Fi and BLE) to enhance the opportunity that the signalwill be received by a nearby listener.

The participant computing devices 906 and 908 can both be programmed topassively monitor for adventure-related broadcast signals over one ormore wireless protocols and, when detected, to request additionalinformation for the on-duty adventure from the system 902 using theidentifier 932. Adventure-related broadcast signals can be encoded withone or more flags (e.g., in the header, in the payload) so that they canreadily be identified as an adventure-related broadcast signal and actedupon by the devices 906 and 908. By using flags, the devices 906 and 908can minimize the number of requests that are transmitted for additionalinformation related to the signals, which can conserve computingresources. Additionally, user settings on the devices 906 and 908 canallow for users to designate whether they want to monitor for andpresent nearby on-duty adventures. If a user does not want toreceive/view on-duty adventures, the devices 906 and 908 will notmonitor for broadcast signals. However, if the devices 906 and 908 haveuser settings to monitor for on-duty adventures, then the devices 906and 908 can register event listeners and can passively monitor foradventure-related broadcast signals.

For example, the guide computing device 904 can run a mobile app that isprogrammed to use one or more wireless beacon protocols (e.g., APPLE'siBeacon, AltBeacon, URlBeacon, GOOGLE Beacons) to transmit BLE beaconsignals that include the identifier 932 in the payload of the beaconmessage. The participant computing devices 906 and 908 can run the sameor similar mobile app that is programmed to passively monitor for BLEbeacon signals and, when detected, to request additional informationfrom the adventure management computer system 902. The BLE beaconsignals can include one or more header fields and/or payload bits thatboth the guide computing device 904 and the participant computingdevices 906, 908 are programmed to recognize as an adventure-relatedbeacon signal, which can help filter beacon signals at the device levelinstead of having to reconcile the beacon signal with a remote system,such as the system 902 and/or a beacon platform that translates beaconidentifiers into additional beacon-related data.

In the depicted example, the participant computing device 906 detectsthe broadcast signal and the identifier 932 from the guide computingdevice 904, and proceeds to request adventure information from thesystem 902 by retransmitting the identifier 938 (step F, 936). Theadventure management system 902 can use the identifier to retrieveinformation for the adventure from the database 910 and can serve theadventure information to the participant computing device 906 (step G,940). The participant computing device 906 can present the adventureinformation in an interface 942 that includes information for theadventure and an option to book the adventure (book now button 944),similar to the interfaces described above with regard to FIGS. 7I-K.User input can be received to book the adventure (step I, 956), whichcan be transmitted to and processed through the system 902 (steps J-K,958-960). The confirmation of the on-duty booking can be transmitted toboth the guide and participant devices 904-906 with correspondingparticipant and guide information 964 and 970 (steps L, 962 and N, 968).The booking and transmission of information after the booking process iscomplete can be similar to the description above with regard to FIGS.6-8, and as depicted in the example interfaces in FIGS. 7L-N. Inresponse to receiving the booking confirmation, the guide computingdevice 904 can stop and/or adjust the broadcast signal that is beingtransmitted (step M, 966). For example, the guide computing device 904may be configured to locally broadcast immediately available adventuresand may stop broadcasting when the guide is not immediately available.In another example, the guide computing device 904 may be configured tochange the identifier to an identifier for the same adventure at a latertime slot in the day so that the guide can continue to locally line-upbookings for the adventure.

Similar to the description above with regard to FIGS. 6-8, the localbroadcast using beacon signals and adventure identifiers can allow forguide transactions to be processed through the system 902 even thoughthe guide and the participant are at the same physical location when theadventure is booked.

Additionally and/or alternatively, the adventure management computersystem 902 can broadcast information about the on-duty adventureparticipant devices, such as the devices 906 and 908. The adventuremanagement computer system 902 can identify devices to receivenotifications about currently available on-duty adventures based on avariety of factors, such as the actual or estimated proximity of theuser to the location of the on-duty adventure, user settings indicatingwhether the user wants to receive notifications about on-dutyadventures, the type of adventures that the user is interested in,and/or other appropriate factors. The location of the user can bedetermined based on a variety of information, such as an adventuremobile app being authorized to use and transmit location information forthe devices 906 and 908, the user having provided their location (e.g.,hometown), location information for the user from other services (e.g.,authorized social media systems), and/or other sources.

For example, the adventure management computer system 902 can broadcastinformation about the on-duty adventure with adventure information 948to the device 908 (step H, 946) in response to the guide computingdevice 904 activating the adventure. The on-duty adventure informationcan be provided on the device 908 as, for example, a push notificationthat includes a brief description of the on-duty adventure that, ifselected by the user, can cause an interface 950 to be presented withinformation on the on-duty adventure. The information can include, forexample, location information 952 (e.g., address, map) for the adventureand an option to book the adventure (book now button 954). Once theon-duty adventure is booked by a user, the system 902 can stop and/ormodify the broadcast for the on-duty adventure, similar to thedescription for the local broadcast.

FIG. 10 is a conceptual diagram of a system 1000 for local adventurebeacon signal transmissions. The system 1000 includes an example guidecomputing device 1002 (similar to the guide computing device 904) and anexample participant computing device 1004 (similar to the participantcomputing device 906). Both the guide computing device 1002 and theparticipant computing device 1004 can include beacon transmission andmonitoring stacks that are similarly programmed to transmit and listenfor beacon signals over a common wireless protocol. For example, theguide computing device 1002 includes an application layer 1006 (e.g.,mobile app) that has obtained an identifier for the adventure that istransmitted in the payload of a beacon signal 1014 through wirelesstransmission layers 1010 and physical layers 1012 on the device 1002.

The beacon signal 1014 is transmitted as a data packet with a header1016, a payload 1018, and a footer 1020. The payload 1018 can includevarious data that is encoded in the payload value 1018, such as throughparticular bit designations in the payload value. For example, thepayload 1018 can include a service ID 1022 that identifies the beaconsignal 1014 as an on-duty adventure beacon signal, an adventure type1024 that is an enumerated value for the type of adventure that is beingadvertised (e.g., hunting, biking, snow), and an identifier for theadventure 1026 that can be used to retrieve information for theadventure from an adventure management computer system. The data values1022 and 1024 can be used by the application layer 1028 and the eventlistener 1030 on the participant computing device 1004 to provide adevice-level filter that efficiently determines whether the device 1004should request additional on-duty adventure information. The beaconsignal can be received at application layer 1028 on the device 1004through physical layers 1034 and wireless transmission layer 1032 on thedevice 1004.

FIG. 11 is a flowchart of an example technique 1100 for providingon-duty adventure broadcasting and booking. The technique 1100 can beperformed, in-part, by an adventure management system 1102 (similar tothe systems 102, 302, 502, 802, 902), a guide computing device 1104(similar to computing devices (similar to computing devices 104, 304,804, 904, 1002), a local participant computing device (similar to thecomputing devices 906 and 1004), and a non-local participant computingdevices (similar to the computing devices 908).

The guide computing device 1104 can activate an on-duty adventure(1110), which can include the guide computing device 1104 transmittingan on-duty activation request to the adventure management computersystem 1102. In response to receiving the on-duty activation request,the adventure management computer system 1102 can generate and registeran identifier for the on-duty adventure (1112) that can be transmittedto the guide computing device 1104 (1114) for local broadcast by theguide computing device 1104 (1116). In the depicted example, the localcomputing device 1106 is located within the local broadcast range of theguide computing device 1104 and can receive the broadcast (1118).However, that same broadcast may not be received by the non-localcomputing device 1108 that is located outside of the local broadcastrange (as indicated by the ‘X’).

In response to receiving the broadcast, which can include the identifierfor the on-duty adventure, the local computing device 1106 can requestadventure information from the adventure management computer system 1102(1120). Such a request can include the identifier locally broadcast bythe guide computing device 1104. The adventure management computersystem 1102 can receive the request and use the adventure identifier toretrieve adventure information (1122) and transmit the adventureinformation to the local computing device 1106 (1126). The localcomputing device 1106 can display the adventure information (1126). Fromthe adventure information, the local computing device 1106 can proceedto book the adventure with the adventure management computer system1102, which can all stem from the local broadcast by the guide computingdevice 1104 that was detected by the local computing device 1106, asdescribed above with regard to FIG. 9.

Optionally, the non-local computing device 1108 can periodically providelocation information to the adventure management computer system 1102(1128), which can at least temporarily store the location informationfor serving location-based adventures to the non-local computing device1108 (1130). For example, in response to the on-duty adventure beingactivated, the adventure management computer system 1102 can identifythat the on-duty adventure is relevant to the non-local computing device1108 and can transmit information for the adventure to the non-localcomputing device 1108 (1132). The adventure management computer system1102 can make such determinations based on any of a variety of factors,such as proximity between a user's current/recent/estimated location andthe location of the on-duty adventure, the user's interest in the typeof adventure (e.g., based on explicitly expressed interests, based onimplicit interests), the user's current availability to participate inthe adventure (e.g., based on accessing an electronic schedule for theuser), and/or combinations thereof. The adventure management computersystem 1102 can perform similar analysis and distribution of on-dutyadventures to the location computing device 1106 as well.

The non-local computing device 1108 can display adventure information(1134), which can include providing an interface through which the usercan book the adventure (1136). The adventure management computer system1102 can book the adventure in response to receiving the booking requestfrom the non-local computing device 1108 (1138) and can proceed totransmit adventure booking confirmations (1140) to both the guidecomputing device 1104 and the non-local computing device 1108. Forexample, the guide computing device 1104 can display the bookingconfirmation (1142), which can include displaying contact informationfor the user of the non-local computing device 1108. Similar display ofconfirmation and contact information for the guide can be presented onthe non-local computing device 1108. In response to receiving thebooking confirmation, the guide computing device 1104 can stop and/ormodify the local broadcasts for the adventure (1144) and the adventuremanagement computer system 1102 can similarly update/modify broadcastsof on-duty adventure information (1146).

FIGS. 12A-M are a set of example screenshots for on-boarding a guide toan adventure management platform through an interface on a mobiledevice, such as a smartphone, tablet computing device, wearablecomputing device (e.g., smartwatch, virtual reality headset, augmentedreality headset), and/or other mobile computing devices. The screenshotsin FIGS. 12A-M are examples of mobile-specific interfaces for onboardinga guide and are designed with specific features and layouts specificallyadapted for ease of use on a mobile device, which generally has asmaller display with one or more touch/presence sensitive surfaces. Theinterfaces in FIGS. 12A-M include layouts and features to permit guidesto be onboarded and to create adventures with minimal time and userinput via mobile device input subsystems on mobile devices (e.g.,touchscreens, buttons), which can be more difficult and cumbersome forusers to provide information than traditional computer input mechanisms,such as keyboards and pointer devices (e.g., mouse). For example, theinput features can laid-out in a vertical arrangements (e.g., allow forready scrolling between features), larger sized buttons and selectableareas can be provided to reduce the granularity with which user inputneeds to be provided (e.g., reduce the precision with which touch inputis provided), buttons and other input features sufficiently spaced apartso as to avoid erroneous inputs (e.g., avoid touch intended for a firstbutton being registered for a second button), and to favor selectableinput features over typing input features, which can reduce the numberof input actions required from users. The interfaces depicted in FIGS.12A-M are similar to the screenshots in FIGS. 4A-S, which can be used onany computing device, including both mobile computing devices and othernon-mobile computing devices (e.g., desktop computers).

Referring to FIG. 12A, a first example GUI 1200 through which a guidecan initially register with an adventure management computer system(e.g., the computer system 102) is depicted. FIG. 12A is similar to FIG.4A, and includes a selectable buttons 1202 at the top and bottom of thepage for initiating the onboarding process, similar to the buttons 402,404. The button 1202 can be positioned at both ends of a verticallyscrolling content page about becoming a guide so as to permit a user toeither immediately initiate the registration process when the page isloaded or to review the content page and then initiate the registrationprocess, which can occur without having to scroll back up to the top ofthe content page.

In response to selecting the buttons 1202, the user can be prompted toprovide login credentials for an example social media platform, asdepicted in FIG. 4B-C. Once authenticated, the social media accountcredentials can be used as login and account information on the platform102, and can be used to automatically obtain and prefill information forthe guide's profile, as depicted in FIG. 12B (similar to FIG. 12D). Forexample, the social media information can be used to prefill one or moreof the fields 1214-1220 (similar to fields 414-420). Once guideinformation is entered, the guide can select the next button 1222(similar to the button 422).

Referring now to FIG. 12C (similar to FIG. 4E), the guide can beprompted to select/set profile and cover photos (1224, similar to 424)that have been populated from the social media data for the guide, andcan be asked to identify other social media accounts that are associatedwith the user (1226, similar to 426). These can be optional fields thata user can fill out. Once ready, the guide can select the finish button1228 (similar to 428).

Referring now to FIG. 12D (similar to FIG. 4F), the guide can beprompted to create his/her first adventure listing, as indicated by thebutton 1230 (similar to button 430). A user who is not intending toinitially act as a guide (but is not precluded from doing so at a laterdate) would not be presented with the option 1230. In response toselecting the button 1230, a first step in creating an adventure listing(identified in the status bar 1232 as “basics”) is presented to theguide with fields 1234-1244 (similar to 434-444_, as depicted in FIG.12E (similar to FIG. 4G). The fields 1234-1244 can be specificallydesigned to include shorter lists of enumerated values that can bereadily selected by a user (e.g., drop-down lists, select forms), tosimplify the guide on-boarding process on mobile devices for guides. Bydoing this, the number of input fields requiring the user to typeinformation, which can be more cumbersome than mere selections, can beminimized in favor of selectable input fields, which can permit a userto provide input via one or more selection inputs. Once the basicinformation for the adventure has been input, the user can select thenext button 1246 (similar to button 446).

Referring now to FIG. 12F (similar to FIG. 4I), additional details forthe adventure are requested via the fields 1250-1254 (similar to450-454). In this example, the guide has provided a description of theexample adventure (1250) and has identified what a user should bring(1252). Once ready, the guide can proceed to the next step by selectinthe next button 1256.

Referring now to FIG. 12G (FIG. 4J), location information for theadventure can be provided via the fields 1258 (similar to 458-462). Thelocation can either be designated in the textual location fields 1258 orthrough the interactive map 1260. Once one is populated, the other canbe determined and automatically populated as well. The location can bethe starting location where participants are to meet the guide toparticipate in the adventure, with more granular instructions on whereto physically meet the guide when they arrive at the location. Onceready, the guide can select the next button 1264 to proceed to the nextstep.

Referring now to FIG. 12H (similar to FIG. 4K), calendar information forthe adventure can be provided via the fields 1268-1280 (similar to468-480). In the depicted example, the guide is able to designate astarting date and time with touch input via the calendar (1278), whichis reflected in text form as 1266. Touch-based selection of the initialcalendar entry for the adventure can be easier and require less inputthan text-based designation of the date. The user can also designateddetails for the adventure vial fields 1268 a-d, which permit designationof times, duration, price, and the pricing type for the adventure. Theuser can also designate the group size (1270) and repetition (1272) forthe adventure, which can be saved/cancelled (1280). Multiple occurrencesof an adventure, including multiple and varied repeating occurrences,can be designated via this interface, as described above with regard toFIGS. 4K-L. Once ready, the user can select the next button 1284.

Referring to FIG. 12I (similar to FIG. 4M), the user can then previewthe adventure and, when ready, can select the finish button 1286(similar to 486). Once uploaded and completed, the adventure may undergoautomatic and/or human review before being officially approved and goinglive on the site.

Once the onboarding process (FIGS. 12A-I) for the guide has beencompleted, the guide can view a customized view of his/her account onthe site. Referring to FIG. 12J (similar to FIG. 4P), a dashboardinterface 1292 (similar to 492) can be presented that includes a listingof all adventures that the guide has created along with statistics,revenue, and other information, along with a button to create anotheradventure.

Referring to FIG. 12K (similar to FIG. 4Q), a passport interface 1294(similar to 494) can be presented, which provides the guide with a listof adventures in which the guide has been a participant on anotherguide's adventure. The passport interface 494 includes upcomingadventures (booked adventures) and a history of adventures.

Referring now to FIG. 12L (similar to FIG. 4R), a profile interface 1296(similar to 496) can be presented to the guide through which the guidecan view his/her profile, associated photos and social media content,and reviews from past participants. The guide can use the profileinterface 1296 to manage his/her public image/presentation to potentialparticipants. Some of all of the information in the interface 1296 canbe accessible to the public.

Referring now to FIG. 12M (similar to FIG. 4S), an account interface1298 (similar to 498) can be presented through which a guide can managehis/her account settings, which can include contact information,security, payment information, payouts, and verification features.

FIG. 13 is a block diagram of computing devices 1300, 1350 that may beused to implement the systems and methods described in this document, aseither a client or as a server or plurality of servers. Computing device1300 is intended to represent various forms of digital computers, suchas laptops, desktops, workstations, personal digital assistants,servers, blade servers, mainframes, and other appropriate computers.Computing device 1350 is intended to represent various forms of mobiledevices, such as personal digital assistants, cellular telephones,smartphones, and other similar computing devices. Additionally computingdevice 1300 or 1350 can include Universal Serial Bus (USB) flash drives.The USB flash drives may store operating systems and other applications.The USB flash drives can include input/output components, such as awireless transmitter or USB connector that may be inserted into a USBport of another computing device. The components shown here, theirconnections and relationships, and their functions, are meant to beexemplary only, and are not meant to limit implementations describedand/or claimed in this document.

Computing device 1300 includes a processor 1302, memory 1304, a storagedevice 1306, a high-speed interface 1308 connecting to memory 1304 andhigh-speed expansion ports 1310, and a low speed interface 1312connecting to low speed bus 1314 and storage device 1306. Each of thecomponents 1302, 1304, 1306, 1308, 1310, and 1312, are interconnectedusing various busses, and may be mounted on a common motherboard or inother manners as appropriate. The processor 1302 can processinstructions for execution within the computing device 1300, includinginstructions stored in the memory 1304 or on the storage device 1306 todisplay graphical information fora GUI on an external input/outputdevice, such as display 1316 coupled to high speed interface 1308. Inother implementations, multiple processors and/or multiple buses may beused, as appropriate, along with multiple memories and types of memory.Also, multiple computing devices 1300 may be connected, with each deviceproviding portions of the necessary operations (e.g., as a server bank,a group of blade servers, or a multi-processor system).

The memory 1304 stores information within the computing device 1300. Inone implementation, the memory 1304 is a volatile memory unit or units.In another implementation, the memory 1304 is a non-volatile memory unitor units. The memory 1304 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

The storage device 1306 is capable of providing mass storage for thecomputing device 1300. In one implementation, the storage device 1306may be or contain a computer-readable medium, such as a floppy diskdevice, a hard disk device, an optical disk device, or a tape device, aflash memory or other similar solid state memory device, or an array ofdevices, including devices in a storage area network or otherconfigurations. A computer program product can be tangibly embodied inan information carrier. The computer program product may also containinstructions that, when executed, perform one or more methods, such asthose described above. The information carrier is a computer- ormachine-readable medium, such as the memory 1304, the storage device1306, or memory on processor 1302.

The high speed controller 1308 manages bandwidth-intensive operationsfor the computing device 1300, while the low speed controller 1312manages lower bandwidth-intensive operations. Such allocation offunctions is exemplary only. In one implementation, the high-speedcontroller 1308 is coupled to memory 1304, display 1316 (e.g., through agraphics processor or accelerator), and to high-speed expansion ports1310, which may accept various expansion cards (not shown). In theimplementation, low-speed controller 1312 is coupled to storage device1306 and low-speed expansion port 1314. The low-speed expansion port,which may include various communication ports (e.g., USB, Bluetooth,Ethernet, wireless Ethernet) may be coupled to one or more input/outputdevices, such as a keyboard, a pointing device, a scanner, or anetworking device such as a switch or router, e.g., through a networkadapter.

The computing device 1300 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 1320, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 1324. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 1322. Alternatively, components from computing device 1300 maybe combined with other components in a mobile device (not shown), suchas device 1350. Each of such devices may contain one or more ofcomputing device 1300, 1350, and an entire system may be made up ofmultiple computing devices 1300, 1350 communicating with each other.

Computing device 1350 includes a processor 1352, memory 1364, aninput/output device such as a display 1354, a communication interface1366, and a transceiver 1368, among other components. The device 1350may also be provided with a storage device, such as a microdrive orother device, to provide additional storage. Each of the components1350, 1352, 1364, 1354, 1366, and 1368, are interconnected using variousbuses, and several of the components may be mounted on a commonmotherboard or in other manners as appropriate.

The processor 1352 can execute instructions within the computing device1350, including instructions stored in the memory 1364. The processormay be implemented as a chipset of chips that include separate andmultiple analog and digital processors. Additionally, the processor maybe implemented using any of a number of architectures. For example, theprocessor 410 may be a CISC (Complex Instruction Set Computers)processor, a RISC (Reduced Instruction Set Computer) processor, or aMISC (Minimal Instruction Set Computer) processor. The processor mayprovide, for example, for coordination of the other components of thedevice 1350, such as control of user interfaces, applications run bydevice 1350, and wireless communication by device 1350.

Processor 1352 may communicate with a user through control interface1358 and display interface 1356 coupled to a display 1354. The display1354 may be, for example, a TFT (Thin-Film-Transistor Liquid CrystalDisplay) display or an OLED (Organic Light Emitting Diode) display, orother appropriate display technology. The display interface 1356 maycomprise appropriate circuitry for driving the display 1354 to presentgraphical and other information to a user. The control interface 1358may receive commands from a user and convert them for submission to theprocessor 1352. In addition, an external interface 1362 may be providein communication with processor 1352, so as to enable near areacommunication of device 1350 with other devices. External interface 1362may provide, for example, for wired communication in someimplementations, or for wireless communication in other implementations,and multiple interfaces may also be used.

The memory 1364 stores information within the computing device 1350. Thememory 1364 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory 1374 may also be provided andconnected to device 1350 through expansion interface 1372, which mayinclude, for example, a SIMM (Single In Line Memory Module) cardinterface. Such expansion memory 1374 may provide extra storage spacefor device 1350, or may also store applications or other information fordevice 1350. Specifically, expansion memory 1374 may includeinstructions to carry out or supplement the processes described above,and may include secure information also. Thus, for example, expansionmemory 1374 may be provide as a security module for device 1350, and maybe programmed with instructions that permit secure use of device 1350.In addition, secure applications may be provided via the SIMM cards,along with additional information, such as placing identifyinginformation on the SIMM card in a non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory,as discussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 1364, expansionmemory 1374, or memory on processor 1352 that may be received, forexample, over transceiver 1368 or external interface 1362.

Device 1350 may communicate wirelessly through communication interface1366, which may include digital signal processing circuitry wherenecessary. Communication interface 1366 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 1368. In addition, short-range communication may occur, suchas using a Bluetooth, Wi-Fi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 1370 mayprovide additional navigation- and location-related wireless data todevice 1350, which may be used as appropriate by applications running ondevice 1350.

Device 1350 may also communicate audibly using audio codec 1360, whichmay receive spoken information from a user and convert it to usabledigital information. Audio codec 1360 may likewise generate audiblesound for a user, such as through a speaker, e.g., in a handset ofdevice 1350. Such sound may include sound from voice telephone calls,may include recorded sound (e.g., voice messages, music files, etc.) andmay also include sound generated by applications operating on device1350.

The computing device 1350 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 1380. It may also be implemented as part of asmartphone 1382, personal digital assistant, or other similar mobiledevice.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), peer-to-peernetworks (having ad-hoc or static members), grid computinginfrastructures, and the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

Although a few implementations have been described in detail above,other modifications are possible. Moreover, other mechanisms forperforming the systems and methods described in this document may beused. In addition, the logic flows depicted in the figures do notrequire the particular order shown, or sequential order, to achievedesirable results. Other steps may be provided, or steps may beeliminated, from the described flows, and other components may be addedto, or removed from, the described systems. Accordingly, otherimplementations are within the scope of the following claims.

1. (canceled)
 2. A guide mobile computing device configured towirelessly communicate with an adventure management computer system tofacilitate connections between an activity guide user and one or moreactivity participants, the guide mobile computing device comprising: atouchscreen interface that outputs a set of activity guide interfacesand is configured to receive touch input of the activity guide user; ageographic location positioning system configured to identify geographiclocation coordinates of the mobile computing device; and an activityguide mobile application stored in a computer-readable memory of theguide mobile computing device that, when executed, causes the guidemobile computing device to: present on the touchscreen interface anactivity listing graphic user interface that prompts the activity guideuser for input into each of: an activity category field, an experiencelevel field for said one or more participants, and a photo selectionfield to upload an image descriptive of the activity category field;responsive to the activity guide user input in the activity listinggraphic user interface, present on the touchscreen interface an activitylocation graphic user interface that includes an interactive mappresented on touchscreen interface which is configured to present ageographic location based on the geographic location coordinatesidentified by the geographic location positioning system of the guidemobile computing device and which is configured to receive touch inputindicative of a start meeting location of the activity guide user;responsive to the activity guide user input in the activity locationgraphic user interface, present on the touchscreen interface an activitycalendar graphic user interface that that prompts the activity guideuser for input into each of: a start date field that includes aninteractive calendar presenting selectable dates, a payment fieldindicative of a price for said one or more participants, a maximum groupsize field, and a recurring adventure field; and after receiving theadventure guide user input in the adventure calendar graphic userinterface, transmit activity opportunity information to adventuremanagement computer system for searching by said one or moreparticipants.
 3. The guide mobile computing device of claim 2, whereinthe adventure guide mobile application stored in the computer-readablememory of the guide mobile computing device that, when executed, furthercauses the guide mobile computing device to: after transmitting activityopportunity information to adventure management computer system forsearching by said one or more participants, present on the touchscreeninterface a participant reservation notification indicative of said oneor more participants reserving an activity for a start date previouslyselected using the activity calendar graphic user interface of the guidemobile computing device.
 4. The guide mobile computing device of claim3, wherein the adventure guide mobile application stored in thecomputer-readable memory of the guide mobile computing device that, whenexecuted, further causes the guide mobile computing device to: updatethe activity calendar graphic user interface of the guide mobilecomputing device in response to receiving the participant reservationnotification indicative of said one or more participants reserving theactivity for the start date previously selected using the activitycalendar graphic user interface of the guide mobile computing device. 5.The guide mobile computing device of claim 4, wherein the adventureguide mobile application stored in the computer-readable memory of theguide mobile computing device that, when executed, further causes theguide mobile computing device to: present on the touchscreen interface apayment notification of said one or more participants reserving theactivity.
 6. The guide mobile computing device of claim 5, wherein theadventure guide mobile application stored in the computer-readablememory of the guide mobile computing device that, when executed, furthercauses the guide mobile computing device to: present on the touchscreeninterface a media share graphic user interface that prompts the activityguide user to select images or video for uploading to the adventuremanagement computer system for sharing with said one or moreparticipants reserving the activity.
 7. The guide mobile computingdevice of claim 3, wherein the adventure guide mobile application storedin the computer-readable memory of the guide mobile computing devicethat, when executed, further causes the guide mobile computing deviceto: present on the touchscreen interface an on-duty activation graphicuser interface that provides a single-button activation to signal thatthe activity guide user is immediately available for on-duty adventureopportunity previously input via the activity listing graphic userinterface.
 8. The guide mobile computing device of claim 7, furthercomprising a first wireless communication means for transmitting to theadventure management computer system a request to activate the on-dutyadventure opportunity to the adventure management computer system, and asecond wireless communication means for transmitting local beaconsignals for detection by proximately positioned mobile computing devicesof said one or more participants, the local beacon signals including atleast a local beacon signal identifier for the activated on-dutyadventure opportunity.
 9. A method of a guide mobile computing device inwireless communication with an adventure management computer system tofacilitate connections between an activity guide user and one or moreactivity participants, the method comprising: presenting on atouchscreen interface of the guide mobile computing device an activitylisting graphic user interface that prompts the activity guide user forinput into each of: an activity category field, an experience levelfield for said one or more participants, and a photo selection field toupload an image descriptive of the activity category field; responsiveto receiving the activity guide user input in the activity listinggraphic user interface, presenting on the touchscreen interface anactivity location graphic user interface that includes an interactivemap presented on touchscreen interface which is configured to present ageographic location based on a geographic location coordinatesidentified by a geographic location positioning system of the guidemobile computing device and which is configured to receive touch inputindicative of a start meeting location of the activity guide user;responsive to receiving the activity guide user input in the activitylocation graphic user interface, presenting on the touchscreen interfacean activity calendar graphic user interface that that prompts theactivity guide user for input into each of: a start date field thatincludes an interactive calendar presenting selectable dates, a paymentfield indicative of a price for said one or more participants, a maximumgroup size field, and a recurring adventure field; and after receivingthe adventure guide user input in the adventure calendar graphic userinterface, transmitting activity opportunity information to adventuremanagement computer system for searching by said one or moreparticipants.
 10. The method of claim 9, further comprising: after saidtransmitting activity opportunity information to adventure managementcomputer system for searching by said one or more participants,presenting on the touchscreen interface a participant reservationnotification indicative of said one or more participants reserving anactivity for a start date previously selected using the activitycalendar graphic user interface of the guide mobile computing device.11. The method of claim 10, further comprising: updating the activitycalendar graphic user interface of the guide mobile computing device inresponse to receiving the participant reservation notificationindicative of said one or more participants reserving the activity forthe start date previously selected using the activity calendar graphicuser interface of the guide mobile computing device.
 12. The method ofclaim 11, further comprising presenting on the touchscreen interface apayment notification of said one or more participants reserving theactivity.
 13. The method of claim 12, further comprising presenting onthe touchscreen interface a media share graphic user interface thatprompts the activity guide user to select images or video for uploadingto the adventure management computer system for sharing with said one ormore participants reserving the activity.
 14. The method of claim 9,further comprising presenting on the touchscreen interface an on-dutyactivation graphic user interface that provides a single-buttonactivation to signal that the activity guide user is immediatelyavailable for on-duty adventure opportunity previously input via theactivity listing graphic user interface.
 15. The method of claim 14,further comprising transmitting from a first wireless communicationchipset of the guide mobile computing device a request to the adventuremanagement computer system to activate the on-duty adventure opportunityto the adventure management computer system.
 16. The method of claim 14,further comprising transmitting from a second wireless communicationchipset local beacon signals for detection by proximately positionedmobile computing devices of said one or more participants, the localbeacon signals including at least a local beacon signal identifier forthe activated on-duty adventure opportunity.